Docker ENTRYPOINT Vs CMD Explained With Examples

In this blog we will look at the key differences between Docker ENTRYPOINT vs CMD instruction using a practical example.

In a Dockerfile, ENTRYPOINT and CMD are two different instructions that are used to define how a container should run.

ENTRYPOINT is used to specify the main command that should be executed when a container is started using the image. The default ENTRYPOINT command is /bin/sh -c

CMD, on the other hand, is used to specify the default command and arguments that should be executed when a container is started.

If both ENTRYPOINT and CMD are specified in a Dockerfile, the command specified in CMD will be appended to the ENTRYPOINT command. It acts as an argument for ENTRYPOINT. The resulting command will be executed when the container is started.

Lets understand these concepts practically.

Let’s take an example of the following Dockerfile. It installs http-tools and starts the ab (apache benchmark) utility using CMD and Entrypoint. Both of them perform the same job

Using CMD

Using ENTRYPOINT: 

Now if you run the container from the above Dockerfile images, it will throw the following error.

The reason is, ab command requires an http endpoint as an argument to start the service.

We have two ways to get around this problem. Hardcode the HTTP endpoint argument as shown in the below examples.

Using CMD: The ab executable and HTTP URL arguments are added in separate square brackets.

Using ENTRYPOINT: The executable and argument are separated by commas in the same square bracket.

Lets look at the difference between CMD and ENTRYPOINT by passing ab commands during docker run.

Using CMD:

While running the container, just add the full ab command at the end of the docker run command. It will override the whole CMD specified in the Dockerfile.

Using ENTRYPOINT:

If you want to pass the URL argument to ENTRYPOINT, you need to pass the URL alone. The reason is we have the ab command as part of the ENTRYPOINT definition.

And the URL you pass in the run command will be appended to the ENTRYPOINT script. In this case, CMD instruction is not required in the Dockerfile.

Docker Command:

You can override the whole ENTRYPOINT like you do with CMD using the --entrypoint flag as shown below

You can also use both CMD and ENTRYPOINT instructions to achieve this. Here is how the Dockerfile looks.

When ENTRYPOINT and CMD used in the same Dockerfile, everything in the CMD instruction will be appended to the ENTRYPOINT as an argument.

If you run a container using the above Dockerfile, at container start, ab script will get executed with the dummy-url.com as an argument.

Lets understand how Docker Entrypoint and CMD translates to Kubernetes Pod.

When it comes to Kubernetes Pod, we have the option named “command” and “args” in the Pod Specification to override Entrypoint and CMD set in the Docker image.

In Kubernetes Pod if you want to override Docker CMD or Entrypoint, you need to specify the command and args show below.

In this example, the entrypoint is set to ["/bin/bash", "-c"], which means that when the container starts, it will run the bash shell with the -c flag to execute the command specified in the command field (my-script.sh). The args field specifies any additional arguments to be passed to my-script.sh.

Here is what you should know.